home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950329-19950528
/
000459_news@columbia.edu_Thu May 25 00:59:07 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA18380
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 25 May 1995 23:12:30 -0400
Received: by apakabar.cc.columbia.edu id AA02060
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 25 May 1995 23:12:29 -0400
Path: news.columbia.edu!news.cs.columbia.edu!news.nyc.pipeline.com!uunet!usc!howland.reston.ans.net!agate!dog.ee.lbl.gov!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit under MS-Windows
Message-Id: <1995May25.065907.52210@cc.usu.edu>
Date: 25 May 95 06:59:07 MDT
References: <3q04p0$1ldu@ns2-1.CC.Lehigh.EDU>
Organization: Utah State University
Lines: 34
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3q04p0$1ldu@ns2-1.CC.Lehigh.EDU>, jmt7@Lehigh.EDU writes:
>
> Hello,
>
> We use Kermit 3.14 very heavily on our campus. From DOS everything
> works great. From MS-Windows, however, sometimes it works but often our
> users will get a message similar to either of these below:
>
> "unknown hardware for port, using..."
>
> - or -
>
> "cannot use RTS/CTS on non-UART ports"
>
> Please note...
>
> 1) the same script will work fine when run under DOS without these
> messages.
>
> 2) we are running Kermit via the .PIF file provided with the software
> (unmodified).
>
> 3) I cannot personally reproduce the above but several of our users
> now have come to me with the same problem (so I can no longer dismiss
> them as nuts!).
--------------
The messages indicate that Kermit found the serial port to be
slightly distasteful and it did not pass inspection. Windows is emulating
the serial port hardware and thus there exist problems in the client's
Windows configuration. That leaves a great many Windows items to explore,
plus checking that the underlying hardware is really free of conflicts.
I wish I had a short list of things to check, but it comes down
to "Windows" items.
Joe D.